Skip to content

ci: allow the deploy workflow to be triggered manually - #53

Merged
leinss merged 1 commit into
releasefrom
feature/deploy-dispatch
Aug 27, 2026
Merged

ci: allow the deploy workflow to be triggered manually#53
leinss merged 1 commit into
releasefrom
feature/deploy-dispatch

Conversation

@leinss

@leinss leinss commented Aug 27, 2026

Copy link
Copy Markdown
Owner

A workflow run can be created with zero jobs attached to it. It then sits in queued indefinitely, and gh run rerun does not recover it: rerun replays the same run object instead of creating a new one. Only a new run object clears the state.

Without workflow_dispatch the only way to produce a new run object is a throwaway commit on the deploy branch. The workflow file lives on the default branch, which is the same branch it deploys from, so the manual trigger is available.

Changes

  • Add workflow_dispatch to the deploy workflow triggers.

Test plan

  • The PR build job runs and passes, which itself confirms job creation works again.
  • After merge, the push run on the deploy branch reaches completed success.
  • gh workflow run against the deploy branch queues a run that gets jobs assigned.

A run can be created with zero jobs attached to it. It then sits in
`queued` indefinitely and `gh run rerun` does not recover it, because
rerun replays the same run object rather than creating a new one. Only a
new run object clears the state.

Without `workflow_dispatch` the only way to produce one is a throwaway
commit on the deploy branch. The default branch is `release`, which is
where the workflow file lives, so the manual trigger is available.
@leinss
leinss merged commit bcbffc2 into release Aug 27, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant